Multi Instance - SubSchedules & Schedule Instance Property
- A Container Job's Job Instance Properties are passed to SubSchedules during build time
- Schedule Instance Properties can be used by Jobs within a SubSchedule
Operations List
Fully-Qualified Naming Scheme
- Typical Naming Scheme:
PrimarySchedule_ContainerJob[SubScheduleName] - Instance Properties for the Primary Schedule and/or SubSchedule can also be included in the fully-qualified Name
- Only the first Instance Property for each component are included in the Name
PrimarySchedule_ContainerJob_ContainerJobInstanceProperty[SubScheduleName]PrimarySchedule_ContainerJob[SubScheduleName_SubScheduleInstanceProperty]
Example
Using Fully Qualified Names
- To update a Global Property, you would use Property Name in the event string:
$PROPERTY:ADD,PropertyName,Value.
- To update a Schedule Instance Property, you would use Fully Qualified Property Name in the event string:
$PROPERTY:ADD,SI."PropertyName".Date."ScheduleName",Value
- To update a SubSchedule Schedule Instance Property, you would use the Fully Qualified Property Name. Here is an event to update multiple layers deep:
$PROPERTY:ADD,SI."PropertyName".[[$DATE]]."PrimarySchedule_ContainerJob_ContainerJobInstanceProperty[SubScheduleName]_ContainerJob2_ContainerJob2Instance[SubSchedule2Name]",Value
Example
Cross SubSchedule Events
- To skip a job in a Schedule, you would use the event string:
$JOB:SKIP,Schedule Date,Schedule Name,Job Name
- To skip a job in a SubSchedule, you would use the event string:
$JOB:SKIP,CURRENT,PrimarySchedule_ContainerJob_ContainerJobInstanceProperty[SubScheduleName],Upload File
